eslint-plugin-jsdoc
JSDoc linting rules for ESLint.
Installation
Install ESLint either locally or globally.
npm install --save-dev eslint
If you have installed ESLint
globally, you have to install JSDoc plugin globally too. Otherwise, install it locally.
npm install --save-dev eslint-plugin-jsdoc
Configuration
Add plugins
section and specify eslint-plugin-jsdoc
as a plugin.
{
"plugins": [
"jsdoc"
]
}
Finally, enable all of the rules that you would like to use.
{
"rules": {
"jsdoc/check-alignment": 1,
"jsdoc/check-examples": 1,
"jsdoc/check-indentation": 1,
"jsdoc/check-param-names": 1,
"jsdoc/check-syntax": 1,
"jsdoc/check-tag-names": 1,
"jsdoc/check-types": 1,
"jsdoc/implements-on-classes": 1,
"jsdoc/match-description": 1,
"jsdoc/newline-after-description": 1,
"jsdoc/no-types": 1,
"jsdoc/no-undefined-types": 1,
"jsdoc/require-description": 1,
"jsdoc/require-description-complete-sentence": 1,
"jsdoc/require-example": 1,
"jsdoc/require-hyphen-before-param-description": 1,
"jsdoc/require-jsdoc": 1,
"jsdoc/require-param": 1,
"jsdoc/require-param-description": 1,
"jsdoc/require-param-name": 1,
"jsdoc/require-param-type": 1,
"jsdoc/require-returns": 1,
"jsdoc/require-returns-check": 1,
"jsdoc/require-returns-description": 1,
"jsdoc/require-returns-type": 1,
"jsdoc/valid-types": 1
}
}
Or you can simply use the following which enables the rules commented
above as "recommended":
{
"extends": ["plugin:jsdoc/recommended"]
}
You can then selectively add to or override the recommended rules.
Options
Rules may, as per the ESLint user guide, have their own individual options. In eslint-plugin-jsdoc
, a few options,
such as, exemptedBy
and contexts
, may be used across different rules.
eslint-plugin-jsdoc
options, if present, are in the form of an object
supplied as the second argument in an array after the error level.
{
rules: {
'jsdoc/require-example': [
'error',
{
avoidExampleOnConstructors: true,
exemptedBy: ['type']
}
]
}
}
Settings
settings.jsdoc.ignorePrivate
- Disables all rules for the comment block
on which a @private
tag (or @access private
) occurs. Defaults to
false
. Note: This has no effect with the rule check-access
(whose
purpose is to check access modifiers).
maxLines
and minLines
One can use minLines
and maxLines
to indicate how many line breaks
(if any) will be checked to find a jsdoc comment block before the given
code block. These settings default to 0
and 1
respectively.
In conjunction with the require-jsdoc
rule, these settings can
be enforced so as to report problems if a jsdoc block is not found within
the specified boundaries. The settings are also used in the fixer to determine
how many line breaks to add when a block is missing.
Mode
settings.jsdoc.mode
- Set to jsdoc
(the default), typescript
, or closure
.
Currently is used for the following:
- Determine valid tags for
check-tag-names
- Only check
@template
in no-undefined-types
for types in "closure" and
"typescript" modes - For type-checking rules, determine which tags will be checked for types
(Closure allows types on some tags which the others do not,
so these tags will additionally be checked in "closure" mode)
- Check preferred tag names
Alias Preference
Use settings.jsdoc.tagNamePreference
to configure a preferred alias name for a JSDoc tag. The format of the configuration is: <primary tag name>: <preferred alias name>
, e.g.
{
"rules": {},
"settings": {
"jsdoc": {
"tagNamePreference": {
"param": "arg",
"returns": "return"
}
}
}
}
One may also use an object with a message
and replacement
.
The following will report the message @extends is to be used over @augments as it is more evocative of classes than @augments
upon encountering @augments
.
{
"rules": {},
"settings": {
"jsdoc": {
"tagNamePreference": {
"augments": {
"message": "@extends is to be used over @augments as it is more evocative of classes than @augments",
"replacement": "extends"
}
}
}
}
}
If one wishes to reject a normally valid tag, e.g., @todo
, one may set the tag to false
:
{
"rules": {},
"settings": {
"jsdoc": {
"tagNamePreference": {
"todo": false
}
}
}
}
A project wishing to ensure no blocks are left excluded from entering the
documentation, might wish to prevent the @ignore
tag in the above manner.
Or one may set the targeted tag to an object with a custom message
, but without a replacement
property:
{
"rules": {},
"settings": {
"jsdoc": {
"tagNamePreference": {
"todo": {
"message": "We expect immediate perfection, so don't leave to-dos in your code."
}
}
}
}
}
Note that the preferred tags indicated in the settings.jsdoc.tagNamePreference
map will be assumed to be defined by check-tag-names
.
Default Preferred Aliases
The defaults in eslint-plugin-jsdoc
(for tags which offer
aliases) are as follows:
@abstract
(over @virtual
)@augments
(over @extends
)@class
(over @constructor
)@constant
(over @const
)@default
(over @defaultvalue
)@description
(over @desc
)@external
(over @host
)@file
(over @fileoverview
, @overview
)@fires
(over @emits
)@function
(over @func
, @method
)@member
(over @var
)@param
(over @arg
, @argument
)@property
(over @prop
)@returns
(over @return
)@throws
(over @exception
)@yields
(over @yield
)
This setting is utilized by the the rule for tag name checking
(check-tag-names
) as well as in the @param
and @require
rules:
check-param-names
check-tag-names
require-hyphen-before-param-description
require-description
require-param
require-param-description
require-param-name
require-param-type
require-returns
require-returns-check
require-returns-description
require-returns-type
@override
/@augments
/@extends
/@implements
Without Accompanying @param
/@description
/@example
/@returns
The following settings allows the element(s) they reference to be omitted
on the JSDoc comment block of the function or that of its parent class
for any of the "require" rules (i.e., require-param
, require-description
,
require-example
, or require-returns
).
settings.jsdoc.overrideReplacesDocs
(@override
) - Defaults to true
settings.jsdoc.augmentsExtendsReplacesDocs
(@augments
or its alias @extends
) - Defaults to false
.settings.jsdoc.implementsReplacesDocs
(@implements
) - Defaults to false
The format of the configuration is as follows:
{
"rules": {},
"settings": {
"jsdoc": {
"overrideReplacesDocs": true,
"augmentsExtendsReplacesDocs": true,
"implementsReplacesDocs": true
}
}
}
Settings to Configure check-types
and no-undefined-types
-
settings.jsdoc.preferredTypes
An option map to indicate preferred
or forbidden types (if default types are indicated here, these will
have precedence over the default recommendations for check-types
).
The keys of this map are the types to be replaced (or forbidden).
These keys may include:
- The "ANY" type,
*
- The pseudo-type
[]
which we use to denote the parent (array)
types used in the syntax string[]
, number[]
, etc. - The pseudo-type
.<>
(or .
) to represent the format Array.<value>
or Object.<key, value>
- The pseudo-type
<>
to represent the format Array<value>
or
Object<key, value>
- A plain string type, e.g.,
MyType
- A plain string type followed by one of the above pseudo-types (except
for
[]
which is always assumed to be an Array
), e.g., Array.
, or
SpecialObject<>
.
If a bare pseudo-type is used, it will match all parent types of that form.
If a pseudo-type prefixed with a type name is used, it will only match
parent types of that form and type name.
The values can be:
false
to forbid the type- a string to indicate the type that should be preferred in its place
(and which
fix
mode can replace); this can be one of the formats
of the keys described above.
- Note that the format will not be changed unless you use a pseudo-type
in the replacement. (For example,
'Array.<>': 'MyArray'
will change
Array.<string>
to MyArray.<string>
, preserving the dot. To get rid
of the dot, you must use the pseudo-type with <>
, i.e.,
'Array.<>': 'MyArray<>'
, which will change Array.<string>
to
MyArray<string>
). - If you use a bare pseudo-type in the replacement (e.g.,
'MyArray.<>': '<>'
), the type will be converted to the format
of the pseudo-type without changing the type name. For example,
MyArray.<string>
will become MyArray<string>
but Array.<string>
will not be modified.
- an object with:
- the key
message
to provide a specific error message
when encountering the discouraged type.
- The message string will have the substrings with special meaning,
{{tagName}}
and {{tagValue}}
, replaced with their
corresponding value.
- an optional key
replacement
with either of the following values:
- a string type to be preferred in its place (and which
fix
mode
can replace) false
(for forbidding the type)
Note that the preferred types indicated as targets in settings.jsdoc.preferredTypes
map will be assumed to be defined by no-undefined-types
.
See the option of check-types
, unifyParentAndChildTypeChecks
, for
how the keys of preferredTypes
may have <>
or .<>
(or just .
)
appended and its bearing on whether types are checked as parents/children
only (e.g., to match Array
if the type is Array
vs. Array.<string>
).
Rules
check-access
Checks that @access
tags use one of the following values:
- "package", "private", "protected", "public"
Also reports:
- Mixing of
@access
with @public
, @private
, @protected
, or @package
on the same doc block. - Use of multiple instances of
@access
(or the @public
, etc. style tags)
on the same doc block.
| |
---|
Context | everywhere |
Tags | @access |
Settings | |
Options | |
The following patterns are considered problems:
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
class MyClass {
myClassField = 1
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
The following patterns are not considered problems:
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
class MyClass {
myClassField = 1
}
function quux (foo) {
}
function quux (foo) {
}
check-alignment
Reports invalid alignment of JSDoc block asterisks.
The following patterns are considered problems:
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
class Foo {
quux(a) {}
}
The following patterns are not considered problems:
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {}
function quux (foo) {
}
function quux (foo) {
}
check-examples
Ensures that (JavaScript) examples within JSDoc adhere to ESLint rules.
Options
The options below all default to no-op/false
except as noted.
captionRequired
JSDoc specs use of an optional <caption>
element at the beginning of
@example
.
The option captionRequired
insists on a <caption>
being present at
the beginning of any @example
.
exampleCodeRegex
and rejectExampleCodeRegex
JSDoc does not specify a formal means for delimiting code blocks within
@example
(it uses generic syntax highlighting techniques for its own
syntax highlighting). The following options determine whether a given
@example
tag will have the check-examples
checks applied to it:
exampleCodeRegex
- Regex which whitelists lintable
examples. If a parenthetical group is used, the first one will be used,
so you may wish to use (?:...)
groups where you do not wish the
first such group treated as one to include. If no parenthetical group
exists or matches, the whole matching expression will be used.
An example might be "^```(?:js|javascript)([\\s\\S]*)```\s*$"
to only match explicitly fenced JavaScript blocks. Defaults to only
using the u
flag, so to add your own flags, encapsulate your
expression as a string, but like a literal, e.g., /```js.*```/gi
.
Note that specifying a global regular expression (i.e., with g
) will
allow independent linting of matched blocks within a single @example
.rejectExampleCodeRegex
- Regex blacklist which rejects
non-lintable examples (has priority over exampleCodeRegex
). An example
might be "^`"
to avoid linting fenced blocks which may indicate
a non-JavaScript language. See exampleCodeRegex
on how to add flags
if the default u
is not sufficient.
If neither is in use, all examples will be matched. Note also that even if
captionRequired
is not set, any initial <caption>
will be stripped out
before doing the regex matching.
paddedIndent
This integer property allows one to add a fixed amount of whitespace at the
beginning of the second or later lines of the example to be stripped so as
to avoid linting issues with the decorative whitespace. For example, if set
to a value of 4
, the initial whitespace below will not trigger indent
rule errors as the extra 4 spaces on each subsequent line will be stripped
out before evaluation.
reportUnusedDisableDirectives
If not set to false
, reportUnusedDisableDirectives
will report disabled
directives which are not used (and thus not needed). Defaults to true
.
Corresponds to ESLint's --report-unused-disable-directives
.
Inline ESLint config within @example
JavaScript is allowed, though the
disabling of ESLint directives which are not needed by the resolved rules
will be reported as with the ESLint --report-unused-disable-directives
command.
Options for Determining ESLint Rule Applicability (allowInlineConfig
, noDefaultExampleRules
, matchingFileName
, configFile
, checkEslintrc
, and baseConfig
)
The following options determine which individual ESLint rules will be
applied to the JavaScript found within the @example
tags (as determined
to be applicable by the above regex options). They are ordered by
decreasing precedence:
allowInlineConfig
- If not set to false
, will allow
inline config within the @example
to override other config. Defaults
to true
.noDefaultExampleRules
- Setting to true
will disable the
default rules which are expected to be troublesome for most documentation
use. See the section below for the specific default rules.configFile
- A config file. Corresponds to ESLint's -c
.matchingFileName
- Option for a file name (even non-existent) to trigger
specific rules defined in one's config; usable with ESLint .eslintrc.*
overrides
-> files
globs, to apply a desired subset of rules with
@example
(besides allowing for rules specific to examples, this option
can be useful for enabling reuse of the same rules within @example
as
with JavaScript Markdown lintable by
other plugins, e.g.,
if one sets matchingFileName
to dummy.md
so that @example
rules will
follow one's Markdown rules).checkEslintrc
- Defaults to true
in adding rules
based on an .eslintrc.*
file. Setting to false
corresponds to
ESLint's --no-eslintrc
.
If matchingFileName
is set, this will automatically be true
and
will use the config corresponding to that file. If matchingFileName
is
not set and this value is set to false
, the .eslintrc.*
configs will
not be checked. If matchingFileName
is not set, and this is unset or
set to true
, the .eslintrc.*
configs will be checked as though the file
name were the same as the file containing the example, with any file
extension changed to ".md" (and if there is no file extension, "dummy.md"
will be used). This allows convenient sharing of similar rules with often
also context-free Markdown as well as use of overrides
as described under
matchingFileName
. Note that this option (whether set by matchingFileName
or set manually to true
) may come at somewhat of a performance penalty
as the file's existence is checked by eslint.baseConfig
- Set to an object of rules with the same schema
as .eslintrc.*
for defaults.
Rules Disabled by Default Unless noDefaultExampleRules
is Set to true
eol-last
- Insisting that a newline "always" be at the end is less likely
to be desired in sample code as with the code file convention.no-console
- This rule is unlikely to have inadvertent temporary debugging
within examples.no-multiple-empty-lines
- This rule may be problematic for projects which
use an initial newline just to start an example. Also, projects may wish to
use extra lines within examples just for easier illustration
purposes.no-undef
- Many variables in examples will be undefined
.no-unused-vars
- It is common to define variables for clarity without always
using them within examples.padded-blocks
- It can generally look nicer to pad a little even if one's
code follows more stringency as far as block padding.import/no-unresolved
- One wouldn't generally expect example paths to
resolve relative to the current JavaScript file as one would with real code.import/unambiguous
- Snippets in examples are likely too short to always
include full import/export info.node/no-missing-import
- See import/no-unresolved
.node/no-missing-require
- See import/no-unresolved
.
| |
---|
Context | everywhere |
Tags | example |
Options | See above |
The following patterns are considered problems:
function quux () {
}
class quux {
}
function quux () {
}
function quux () {
}
var quux = {
};
function quux () {
}
function quux () {
}
function quux2 () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {}
function quux () {}
function quux2 () {
}
function quux2 () {
}
function quux2 () {
}
function quux2 () {
}
function quux2 () {
}
function quux2 () {
}
function quux2 () {
}
function quux () {
}
function f () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
The following patterns are not considered problems:
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {}
function quux () {}
var quux = {
};
function quux () {}
function quux () {
}
function quux2 () {
}
function quux () {
}
check-indentation
Reports invalid padding inside JSDoc blocks.
Ignores parts enclosed in Markdown "code block"'s. For example,
the following description is not reported:
Options
This rule has an object option.
excludeTags
Array of tags (e.g., ['example', 'description']
) whose content will be
"hidden" from the check-indentation
rule. Defaults to ['example']
.
By default, the whole JSDoc block will be checked for invalid padding.
That would include @example
blocks too, which can get in the way
of adding full, readable examples of code without ending up with multiple
linting issues.
When disabled (by passing excludeTags: []
option), the following code will
report a padding issue:
| |
---|
Context | everywhere |
Tags | N/A |
Options | excludeTags |
The following patterns are considered problems:
function quux () {
}
function quux () {
}
class Moo {}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
The following patterns are not considered problems:
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
check-param-names
Ensures that parameter names in JSDoc match those in the function declaration.
Options
If set to true
, this option will allow extra @param
definitions (e.g.,
representing future expected or virtual params) to be present without needing
their presence within the function signature. Other inconsistencies between
@param
's and present function parameters will still be reported.
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression |
Options | allowExtraTrailingParamDocs |
Tags | param |
The following patterns are considered problems:
function quux (foo = 'FOO') {
}
function quux (foo = 'FOO') {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function assign (employees) {
};
function assign (employees) {
};
function quux (bar, foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo, bar) {
}
function quux (foo, foo) {
}
function quux ({foo, bar}) {
}
function quux ({foo, bar}, baz) {
}
function quux ({foo, bar}, baz) {
}
export class SomeClass {
constructor(private property: string) {}
}
function quux (foo) {
}
function quux (error, cde = 1) {
};
The following patterns are not considered problems:
function quux (foo) {
}
function quux (foo) {
}
function quux (foo, bar) {
}
function quux (foo, bar, baz) {
}
function quux (foo, bar) {
}
function quux (...args) {
}
function quux ({a, b}) {
}
function quux (foo, bar) {
}
function quux ({a, b} = {}) {
}
function quux ([a, b] = []) {
}
function assign (employees) {
};
export class SomeClass {
constructor(private property: string) {}
}
function quux (error, code = 1) {
};
function quux (foo) {
}
Deconstructing Function Parameter
eslint-plugin-jsdoc
does not validate names of parameters in function deconstruction, e.g.
function quux ({
a,
b
}) {
}
{a, b}
is an ObjectPattern
AST type and does not have a name. Therefore, the associated parameter in JSDoc block can have any name.
Likewise for the pattern [a, b]
which is an ArrayPattern
.
check-property-names
Ensures that property names in JSDoc are not duplicated on the same block
and that nested properties have defined roots.
Options
| |
---|
Context | Everywhere |
Tags | property |
The following patterns are considered problems:
function quux ({foo, bar}) {
}
function quux ({foo, bar}, baz) {
}
function quux ({foo, bar}, baz) {
}
The following patterns are not considered problems:
function quux (code = 1) {
this.error = new Error('oops');
this.code = code;
}
check-syntax
Reports against Google Closure Compiler syntax.
The following patterns are considered problems:
function quux (foo) {
}
The following patterns are not considered problems:
function quux (foo) {
}
function quux (foo) {
}
check-tag-names
Reports invalid block tag names.
Valid JSDoc 3 Block Tags are:
abstract
access
alias
async
augments
author
borrows
callback
class
classdesc
constant
constructs
copyright
default
deprecated
description
enum
event
example
exports
external
file
fires
function
generator
global
hideconstructor
ignore
implements
inheritdoc
inner
instance
interface
kind
lends
license
listens
member
memberof
memberof!
mixes
mixin
module
name
namespace
override
package
param
private
property
protected
public
readonly
requires
returns
see
since
static
summary
this
throws
todo
tutorial
type
typedef
variation
version
yields
modifies
is also supported (see source) but is undocumented.
The following synonyms are also recognized:
arg
argument
const
constructor
defaultvalue
desc
emits
exception
extends
fileoverview
func
host
method
overview
prop
return
var
virtual
yield
For TypeScript
(or Closure), when settings.jsdoc.mode
is set to typescript
or closure
,
one may also use the following:
template
And for Closure,
when settings.jsdoc.mode
is set to closure
, one may use the following (in
addition to the jsdoc and TypeScript tags):
define (synonym of `const` per jsdoc source)
dict
export
externs
final
implicitCast (casing distinct from that recognized by jsdoc internally)
inheritDoc (casing distinct from that recognized by jsdoc internally)
noalias
nocollapse
nocompile
noinline
nosideeffects
polymer
polymerBehavior
preserve
record (synonym of `interface` per jsdoc source)
struct
suppress
unrestricted
...and these undocumented tags which are only in source:
closurePrimitive
customElement
expose
hidden
idGenerator
meaning
mixinClass
mixinFunction
ngInject
owner
typeSummary
wizaction
Note that the tags indicated as replacements in settings.jsdoc.tagNamePreference
will automatically be considered as valid.
Options
definedTags
Use an array of definedTags
strings to configure additional, allowed tags.
The format is as follows:
{
"definedTags": ["note", "record"]
}
| |
---|
Context | everywhere |
Tags | N/A |
Options | definedTags |
Settings | tagNamePreference , mode |
The following patterns are considered problems:
let a;
function quux () {
}
function quux () {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux (foo) {}
function quux (foo) {}
function quux (foo) {}
The following patterns are not considered problems:
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {}
function quux (foo) {}
function quux (foo) {}
function quux (foo) {
}
function quux () {
}
function quux () {
}
export function transient<T>(target?: T): T {
}
check-types
Reports invalid types.
By default, ensures that the casing of native types is the same as in this list:
undefined
null
boolean
number
bigint
string
symbol
object
Array
Function
Date
RegExp
Options
check-types
allows one option:
- An option object:
- with the key
noDefaults
to insist that only the supplied option type
map is to be used, and that the default preferences (such as "string"
over "String") will not be enforced. The option's default is false
. - with the key
exemptTagContexts
which will avoid reporting when a
bad type is found on a specified tag. Set to an array of objects with
a key tag
set to the tag to exempt, and a types
key which can
either be true
to indicate that any types on that tag will be allowed,
or to an array of strings which will only allow specific bad types.
If an array of strings is given, these must match the type exactly,
e.g., if you only allow "object"
, it will not allow
"object<string, string>"
. Note that this is different from the
behavior of settings.jsdoc.preferredTypes
. This option is useful
for normally restricting generic types like object
with
preferredTypes
, but allowing typedef
to indicate that its base
type is object
. - with the key
unifyParentAndChildTypeChecks
which will treat
settings.jsdoc.preferredTypes
keys such as SomeType
as matching
not only child types such as an unadorned SomeType
but also
SomeType<aChildType>
, SomeType.<aChildType>
, or if SomeType
is
Array
(or []
), it will match aChildType[]
. If this is false
or
unset, the former format will only apply to types which are not parent
types/unions whereas the latter formats will only apply for parent
types/unions. The special types []
, .<>
(or .
), and <>
act only as parent types (and will not match a bare child type such as
Array
even when unified, though, as mentioned, Array
will match
say string[]
or Array.<string>
when unified). The special type
*
is only a child type. Note that there is no detection of parent
and child type together, e.g., you cannot specify preferences for
string[]
specifically as distinct from say number[]
, but you can
target both with []
or the child types number
or string
.
See also the documentation on settings.jsdoc.preferredTypes
which impacts
the behavior of check-types
.
Why not capital case everything?
Why are boolean
, number
and string
exempt from starting with a capital letter? Let's take string
as an example. In Javascript, everything is an object. The string Object has prototypes for string functions such as .toUpperCase()
.
Fortunately we don't have to write new String()
everywhere in our code. Javascript will automatically wrap string primitives into string Objects when we're applying a string function to a string primitive. This way the memory footprint is a tiny little bit smaller, and the GC has less work to do.
So in a sense, there two types of strings in Javascript; {string}
literals, also called primitives and {String}
Objects. We use the primitives because it's easier to write and uses less memory. {String}
and {string}
are technically both valid, but they are not the same.
new String('lard')
'lard'
new String('lard') === 'lard'
To make things more confusing, there are also object literals and object Objects. But object literals are still static Objects and object Objects are instantiated Objects. So an object primitive is still an object Object.
However, Object.create(null)
objects are not instanceof Object
, however, so
in the case of this Object we lower-case to indicate possible support for
these objects.
Basically, for primitives, we want to define the type as a primitive, because that's what we use in 99.9% of cases. For everything else, we use the type rather than the primitive. Otherwise it would all just be {object}
.
In short: It's not about consistency, rather about the 99.9% use case. (And some
functions might not even support the objects if they are checking for identity.)
type name | typeof | check-types | testcase |
---|
Array | object | Array | ([]) instanceof Array -> true |
Function | function | function | (function f () {}) instanceof Function -> true |
Date | object | Date | (new Date()) instanceof Date -> true |
RegExp | object | RegExp | (new RegExp(/.+/)) instanceof RegExp -> true |
Object | object | object | ({}) instanceof Object -> true but Object.create(null) instanceof Object -> false |
Boolean | boolean | boolean | (true) instanceof Boolean -> false |
Number | number | number | (41) instanceof Number -> false |
String | string | string | ("test") instanceof String -> false |
| |
---|
Context | everywhere |
Tags | augments , class , constant , enum , implements , member , module , namespace , param , property , returns , throws , type , typedef , yields |
Aliases | constructor , const , extends , var , arg , argument , prop , return , exception , yield |
Closure-only | package , private , protected , public , static |
Options | noDefaults , exemptTagContexts , unifyParentAndChildTypeChecks |
Settings | preferredTypes , mode |
The following patterns are considered problems:
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux () {
}
function quux (foo, bar, baz) {
}
function quux (foo, bar, baz) {
}
function quux (foo, bar, baz) {
}
function qux(foo) {
}
function qux(foo) {
}
function qux(foo) {
}
function qux(foo, bar, baz) {
}
function qux(foo) {
}
function qux(foo) {
}
function qux(foo, bar) {
}
function qux(foo, bar) {
}
function qux(foo) {
}
function qux(foo) {
}
function qux(baz) {
}
function qux(baz) {
}
function qux(foo, bar) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux () {}
function quux () {}
The following patterns are not considered problems:
function quux (foo, bar, baz) {
}
function quux (foo, bar, baz) {
}
function quux (foo, bar, baz) {
}
function qux(foo) {
}
function qux(foo) {
}
function qux(foo) {
}
function qux(foo) {
}
function quux () {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
var subscribe = function(callback) {};
function quux () {}
function quux () {}
check-values
This rule checks the values for a handful of tags:
@version
- Checks that there is a present and valid
semver version value.@since
- As with @version
@license
- Checks that there is a present and valid SPDX identifier
or is present within an allowedLicenses
option.@author
- Checks there is a value present, and if the option
allowedAuthors
is present, ensure that the author value is one
of these array items.
Options
allowedAuthors
An array of allowable author values. If absent, only non-whitespace will
be checked for.
allowedLicenses
An array of allowable license values or true
to allow any license text.
If present as an array, will be used in place of SPDX identifiers.
licensePattern
A string to be converted into a RegExp
(with u
flag) and whose first
parenthetical grouping, if present, will match the portion of the license
description to check (if no grouping is present, then the whole portion
matched will be used). Defaults to ([^\n]*)
, i.e., the SPDX expression
is expected before any line breaks.
| |
---|
Context | everywhere |
Tags | @version , @since , @license , @author |
Options | allowedAuthors , allowedLicenses , licensePattern |
Settings | tagNamePreference |
The following patterns are considered problems:
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
Some extra text"; expected SPDX expression: https://spdx.org/licenses/.
/**
* @author
*/
function quux (foo) {
}
// Message: Missing JSDoc @author.
/**
* @author Brett Zamir
*/
function quux (foo) {
}
// Options: [{"allowedAuthors":["Gajus Kuizinas","golopot"]}]
// Message: Invalid JSDoc @author: "Brett Zamir"; expected one of Gajus Kuizinas, golopot.
The following patterns are not considered problems:
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
empty-tags
Expects the following tags to be empty of any content:
@abstract
@async
@generator
@global
@hideconstructor
@ignore
@inheritdoc
@inner
@instance
@override
@readonly
The following will also be expected to be empty unless settings.jsdoc.mode
is set to "closure" (which allows types).
@package
@private
@protected
@public
@static
Note that @private
will still be checked for content by this rule even with
settings.jsdoc.ignorePrivate
set to true
(a setting which normally
causes rules not to take effect).
Options
tags
If you want additional tags to be checked for their descriptions, you may
add them within this option.
{
'jsdoc/empty-tags': ['error', {tags: ['event']}]
}
| |
---|
Context | everywhere |
Tags | and others added by tags |
Aliases | |
Options | tags |
The following patterns are considered problems: | |
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
The following patterns are not considered problems:
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
implements-on-classes
Reports an issue with any non-constructor function using @implements
.
Constructor functions, whether marked with @class
, @constructs
, or being
an ES6 class constructor, will not be flagged.
To indicate that a function follows another function's signature, one might
instead use @type
to indicate the @function
or @callback
to which the
funciton is adhering.
Options
contexts
Set this to an array of strings representing the AST context
where you wish the rule to be applied.
Overrides the default contexts (see below). Set to "any"
if you want
the rule to apply to any jsdoc block throughout your files (as is necessary
for finding function blocks not attached to a function declaration or
expression, i.e., @callback
or @function
(or its aliases @func
or
@method
) (including those associated with an @interface
).
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression ; others when contexts option enabled |
Tags | implements (prevented) |
Options | contexts |
The following patterns are considered problems:
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
The following patterns are not considered problems:
function quux () {
}
function quux () {
}
function quux () {
}
class quux {
constructor () {
}
}
const quux = class {
constructor () {
}
}
function quux () {
}
function quux () {
}
match-description
Enforces a regular expression pattern on descriptions.
The default is this basic expression to match English sentences (Support
for Unicode upper case may be added in a future version when it can be handled
by our supported Node versions):
^([A-Z]|[`\\d_])[\\s\\S]*[.?!`]$
Applies to the jsdoc block description and @description
(or @desc
)
by default but the tags
option (see below) may be used to match other tags.
Options
matchDescription
You can supply your own expression to override the default, passing a
matchDescription
string on the options object.
{
'jsdoc/match-description': ['error', {matchDescription: '[A-Z].*\\.'}]
}
As with the default, the supplied regular expression will be applied with the
Unicode ("u"
) flag and is not case-insensitive.
tags
If you want different regular expressions to apply to tags, you may use
the tags
option object:
{
'jsdoc/match-description': ['error', {tags: {
param: '\\- [A-Z].*\\.',
returns: '[A-Z].*\\.'
}}]
}
In place of a string, you can also add true
to indicate that a particular
tag should be linted with the matchDescription
value (or the default).
{
'jsdoc/match-description': ['error', {tags: {
param: true,
returns: true
}}]
}
The tags @param
/@arg
/@argument
and @property
/@prop
will be properly
parsed to ensure that the matched "description" text includes only the text
after the name.
All other tags will treat the text following the tag name, a space, and
an optional curly-bracketed type expression (and another space) as part of
its "description" (e.g., for @returns {someType} some description
, the
description is some description
while for @some-tag xyz
, the description
is xyz
).
mainDescription
If you wish to override the main function description without changing the
default match-description
, you may use mainDescription
:
{
'jsdoc/match-description': ['error', {
mainDescription: '[A-Z].*\\.',
tags: {
param: true,
returns: true
}
}]
}
There is no need to add mainDescription: true
, as by default, the main
function (and only the main function) is linted, though you may disable checking
it by setting it to false
.
contexts
Set this to an array of strings representing the AST context
where you wish the rule to be applied (e.g., ClassDeclaration
for ES6 classes).
Overrides the default contexts (see below). Set to "any"
if you want
the rule to apply to any jsdoc block throughout your files.
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression ; others when contexts option enabled |
Tags | docblock and @description by default but more with tags |
Aliases | @desc |
Settings | |
Options | contexts , tags (accepts tags with names and optional type such as 'param', 'arg', 'argument', 'property', and 'prop', and accepts arbitrary list of other tags with an optional type (but without names), e.g., 'returns', 'return'), mainDescription , matchDescription |
The following patterns are considered problems:
const q = class {
}
const q = {
};
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux (foo) {
}
function quux (foo) {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function longDescription (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux () {
}
function quux () {
}
class quux {
}
class MyClass {
myClassField = 1
}
interface quux {
}
const myObject = {
myProp: true
};
function quux (foo) {
}
function quux (foo) {
}
The following patterns are not considered problems:
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
class quux {
}
class quux {
}
class MyClass {
myClassField = 1
}
interface quux {
}
const myObject = {
myProp: true
};
const q = class {
}
const q = {
};
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux (foo) {
}
function quux (foo) {
}
function quux () {
}
newline-after-description
Enforces a consistent padding of the block description.
Options
This rule allows one optional string argument. If it is "always"
then a problem is raised when there is no newline after the description. If it is "never"
then a problem is raised when there is a newline after the description. The default value is "always"
.
| |
---|
Context | everywhere |
Options | (a string matching `"always" |
Tags | N/A (doc block) |
The following patterns are considered problems:
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
The following patterns are not considered problems:
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
export function parseQueryString(queryString: string): { [key: string]: string } {
}
no-types
This rule reports types being used on @param
or @returns
.
The rule is intended to prevent the indication of types on tags where
the type information would be redundant with TypeScript.
Options
contexts
Set this to an array of strings representing the AST context
where you wish the rule to be applied.
Overrides the default contexts (see below). Set to "any"
if you want
the rule to apply to any jsdoc block throughout your files (as is necessary
for finding function blocks not attached to a function declaration or
expression, i.e., @callback
or @function
(or its aliases @func
or
@method
) (including those associated with an @interface
).
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression ; others when contexts option enabled |
Tags | param , returns |
Aliases | arg , argument , return |
Options | contexts |
The following patterns are considered problems:
function quux (foo) {
}
function quux (foo) {
}
function quux () {
}
The following patterns are not considered problems:
function quux (foo) {
}
no-undefined-types
Checks that types in jsdoc comments are defined. This can be used to check
unimported types.
When enabling this rule, types in jsdoc comments will resolve as used
variables, i.e. will not be marked as unused by no-unused-vars
.
In addition to considering globals found in code (or in ESLint-indicated
globals
) as defined, the following tags will also be checked for
name(path) definitions to also serve as a potential "type" for checking
the tag types in the table below:
@callback
, @class
(or @constructor
), @constant
(or @const
), @event
, @external
(or @host
), @function
(or @func
or @method
), @interface
, @member
(or @var
), @mixin
, @name
, @namespace
, @template
(for "closure" or "typescript" settings.jsdoc.mode
only), @typedef
.
The following tags will also be checked but only when the mode is closure
:
@package
, @private
, @protected
, @public
, @static
The following types are always considered defined.
null
, undefined
, void
, string
, boolean
, object
,
function
, symbol
number
, bigint
, NaN
, Infinity
any
, *
Array
, Object
, RegExp
, Date
, Function
Note that preferred types indicated within settings.jsdoc.preferredTypes
will
also be assumed to be defined.
Options
An option object may have the following key:
definedTypes
- This array can be populated to indicate other types which
are automatically considered as defined (in addition to globals, etc.).
Defaults to an empty array.
| |
---|
Context | everywhere |
Tags | augments , class , constant , enum , implements , member , module , namespace , param , property , returns , throws , type , typedef , yields |
Aliases | constructor , const , extends , var , arg , argument , prop , return , exception , yield |
Closure-only | package , private , protected , public , static |
Options | definedTypes |
Settings | preferredTypes , mode |
The following patterns are considered problems:
function quux(foo, bar, baz) {
}
function quux(foo, bar, baz) {
}
function quux(foo) {
}
function quux(foo, bar) {
}
function quux(foo, bar, baz) {
}
function quux(foo, bar, baz) {
}
function foo (bar) {
};
class Foo {
bar () {
}
}
class Foo {
invalidTemplateReference () {
}
}
class Bar {
validTemplateReference () {
}
}
var quux = {
};
class Foo {
bar (baz) {
}
}
function quux (varargs) {
}
function quux () {}
function quux () {}
The following patterns are not considered problems:
function quux(foo) {
}
function quux(foo) {
}
class MyClass {}
function quux(foo) {
console.log(foo);
}
quux(0);
const MyType = require('my-library').MyType;
function quux(foo) {
}
const MyType = require('my-library').MyType;
function quux(foo) {
}
import {MyType} from 'my-library';
function quux(foo, bar, baz) {
}
function quux(foo, bar) {
}
function quux(foo) {
}
function quux(foo) {
}
function testFunction(callback) {
callback();
}
function foo () {
}
function foo () {
}
function quux(foo, bar) {
}
function quux(foo, bar, baz) {
}
function quux(foo, bar, baz) {
}
function foo (bar) {
};
class Foo {
bar () {
}
}
class Foo {
bar () {}
baz () {}
}
class Foo {
bar (baz) {
}
}
function quux () {
}
function registerEvent(obj, method, callback) {
}
function quux (varargs) {
}
function quux (varargs) {
}
class Navigator {}
function quux () {}
class SomeType {}
function quux () {}
require-description-complete-sentence
Requires that block description, explicit @description
, and @param
/@returns
tag descriptions are written in complete sentences, i.e.,
- Description must start with an uppercase alphabetical character.
- Paragraphs must start with an uppercase alphabetical character.
- Sentences must end with a period.
- Every line in a paragraph (except the first) which starts with an uppercase
character must be preceded by a line ending with a period.
- A colon or semi-colon followed by two line breaks is still part of the
containing paragraph (unlike normal dual line breaks).
- Text within inline tags
{...}
are not checked for sentence divisions. - Periods after items within the
abbreviations
option array are not treated
as sentence endings.
Options
tags
If you want additional tags to be checked for their descriptions, you may
add them within this option.
{
'jsdoc/require-description-complete-sentence': ['error', {tags: ['see', 'copyright']}]
}
The tags @param
/@arg
/@argument
and @property
/@prop
will be properly
parsed to ensure that the checked "description" text includes only the text
after the name.
All other tags will treat the text following the tag name, a space, and
an optional curly-bracketed type expression (and another space) as part of
its "description" (e.g., for @returns {someType} some description
, the
description is some description
while for @some-tag xyz
, the description
is xyz
).
abbreviations
You can provide an abbreviations
options array to avoid such strings of text
being treated as sentence endings when followed by dots. The .
is not
necessary at the end of the array items.
| |
---|
Context | everywhere |
Tags | doc block, param , returns , description , property , summary , file , classdesc , todo , deprecated , throws , 'yields' and others added by tags |
Aliases | arg , argument , return , desc , prop , fileoverview , overview , exception , yield |
Options | tags , abbreviations |
The following patterns are considered problems: | |
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function longDescription (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux (foo) {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
The following patterns are not considered problems:
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
**
* Do not have dynamic content; e.g. homepage. Here a simple unique id
* suffices.
*/
function quux () {
}
require-description
Requires that all functions have a description.
- All functions must have an implicit description or have the option
descriptionStyle
set to tag
. - Every jsdoc block description (or description tag if
descriptionStyle
is
"tag"
) must have a non-empty description that explains the purpose of the
method.
Options
An options object may have any of the following properties:
contexts
- Set to an array of strings representing the AST context
where you wish the rule to be applied (e.g., ClassDeclaration
for ES6
classes). Overrides the default contexts (see below). Set to "any"
if
you want the rule to apply to any jsdoc block throughout your files.exemptedBy
- Array of tags (e.g., ['type']
) whose presence on the
document block avoids the need for a @description
. Defaults to an
empty array.descriptionStyle
- Whether to accept implicit descriptions ("body"
) or
@description
tags ("tag"
) as satisfying the rule. Set to "any"
to
accept either style. Defaults to "body"
.
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression ; others when contexts option enabled |
Tags | description or jsdoc block |
Aliases | desc |
Options | contexts , exemptedBy , descriptionStyle |
Settings | overrideReplacesDocs , augmentsExtendsReplacesDocs , implementsReplacesDocs |
The following patterns are considered problems:
function quux () {
}
function quux () {
}
function quux () {
}
class quux {
}
class quux {
}
class quux {
}
function quux () {
}
interface quux {
}
var quux = class {
};
var quux = {
};
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
The following patterns are not considered problems:
function quux () {
}
function quux () {
}
function quux () {
}
class quux {
}
function quux () {
}
function quux () {
}
interface quux {
}
var quux = class {
};
var quux = {
};
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
require-example
Requires that all functions have examples.
- All functions must have one or more
@example
tags. - Every example tag must have a non-empty description that explains the method's usage.
Options
This rule has an object option.
exemptedBy
Array of tags (e.g., ['type']
) whose presence on the document
block avoids the need for an @example
. Defaults to an empty array.
avoidExampleOnConstructors
Set to true
to avoid the need for an example on a constructor (whether
indicated as such by a jsdoc tag or by being within an ES6 class
).
Defaults to false
.
contexts
Set this to an array of strings representing the AST context
where you wish the rule to be applied (e.g., ClassDeclaration
for ES6 classes).
Overrides the default contexts (see below). Set to "any"
if you want
the rule to apply to any jsdoc block throughout your files.
Fixer
The fixer for require-example
will add an empty @example
, but it will still
report a missing example description after this is added.
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression ; others when contexts option enabled |
Tags | example |
Options | exemptedBy , avoidExampleOnConstructors , contexts |
Settings | overrideReplacesDocs , augmentsExtendsReplacesDocs , implementsReplacesDocs |
The following patterns are considered problems:
function quux () {
}
function quux () {
}
function f () {
}
function quux () {
}
function quux () {
}
class quux {
}
function quux () {
}
The following patterns are not considered problems:
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
class Foo {
constructor () {
}
}
function quux () {
}
function quux () {
}
class quux {
}
function quux () {
}
require-file-overview
Checks that:
- All files have a
@file
, @fileoverview
, or @overview
tag. - Duplicate file overview tags within a given file will be reported
- File overview tags will be reported which are not, as per
the docs, "at the beginning of
the file"–where beginning of the file is interpreted in this rule
as being when the overview tag is not preceded by anything other than
a comment.
Options
tags
The keys of this object are tag names, and the values are configuration
objects indicating what will be checked for these whole-file tags.
Each configuration object has the following boolean keys (which default
to false
when this option is supplied): mustExist
, preventDuplicates
,
initialCommentsOnly
. These correspond to the three items above.
When no tags
is present, the default is:
{
"file": {
"initialCommentsOnly": true,
"mustExist": true,
"preventDuplicates": true,
}
}
You can add additional tag names and/or override file
if you supply this
option, e.g., in place of or in addition to file
, giving other potential
file global tags like @license
, @copyright
, @author
, @module
or
@exports
, optionally restricting them to a single use or preventing them
from being preceded by anything besides comments.
For example:
{
"license": {
"mustExist": true,
"preventDuplicates": true,
}
}
This would require one and only one @license
in the file, though because
initialCommentsOnly
is absent and defaults to false
, the @license
can be anywhere.
In the case of @license
, you can use this rule along with the
check-values
rule (with its allowedLicenses
or licensePattern
options),
to enforce a license whitelist be present on every JS file.
Note that if you choose to use preventDuplicates
with license
, you still
have a way to allow multiple licenses for the whole page by using the SPDX
"AND" expression, e.g., @license (MIT AND GPL-3.0)
.
Note that the tag names are the main jsdoc tag name, so you should use file
in this configuration object regardless of whether you have configured
fileoverview
instead of file
on tagNamePreference
(i.e., fileoverview
will be checked, but you must use file
on the configuration object).
| |
---|
Context | Everywhere |
Tags | file ; others when tags set |
Aliases | fileoverview , overview |
Options | tags |
The following patterns are considered problems:
function quux () {}
function quux () {}
function quux () {}
function quux () {}
function quux () {}
function quux () {}
function quux (a) {}
function quux (a) {}
function bar (b) {}
function quux () {
}
function quux () {
}
function quux () {
}
The following patterns are not considered problems:
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
var a
require-hyphen-before-param-description
Requires a hyphen before the @param
description.
Options
This rule takes one optional string argument and an optional options object.
If the string is "always"
then a problem is raised when there is no hyphen
before the description. If it is "never"
then a problem is raised when there
is a hyphen before the description. The default value is "always"
.
The options object may have the following properties:
checkProperties
- Boolean on whether to also apply the rule to @property
tags.
| |
---|
Context | everywhere |
Tags | param and optionally property |
Aliases | arg , argument ; optionally prop |
Options | (a string matching `"always" |
The following patterns are considered problems:
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux (foo) {
}
The following patterns are not considered problems:
function quux () {
}
function quux () {
}
function quux () {
}
require-jsdoc
Checks for presence of jsdoc comments, on class declarations as well as
functions.
Options
Accepts one optional options object with the following optional keys.
-
publicOnly
- This option will insist that missing jsdoc blocks are
only reported for function bodies / class declarations that are exported
from the module. May be a boolean or object. If set to true
, the defaults
below will be used. If unset, jsdoc block reporting will not be limited to
exports.
This object supports the following optional boolean keys (false
unless
otherwise noted):
ancestorsOnly
- Only check node ancestors to check if node is exportedesm
- ESM exports are checked for JSDoc comments (Defaults to true
)cjs
- CommonJS exports are checked for JSDoc comments (Defaults to true
)window
- Window global exports are checked for JSDoc comments
-
require
- An object with the following optional boolean keys which all
default to false
except as noted, indicating the contexts where the rule
will apply:
ArrowFunctionExpression
ClassDeclaration
ClassExpression
FunctionDeclaration
(defaults to true
)FunctionExpression
MethodDefinition
-
contexts
- Set this to an array of strings representing the additional
AST contexts where you wish the rule to be applied (e.g., Property
for
properties). Defaults to an empty array.
-
exemptEmptyFunctions
(default: false) - When true
, the rule will not report
missing jsdoc blocks above functions/methods with no parameters or return values
(intended where variable names are sufficient for themselves as documentation).
| |
---|
Context | ArrowFunctionExpression , ClassDeclaration , ClassExpression , FunctionDeclaration , FunctionExpression ; others when contexts option enabled |
Tags | N/A |
Options | publicOnly , require , contexts , exemptEmptyFunctions |
The following patterns are considered problems:
function myFunction() {
}
function myFunction() {
}
function myFunction() {
}
export var test = function () {
};
function test () {
}
export var test2 = test;
export const test = () => {
};
export let test = class {
};
export default function () {}
export default () => {}
export default (function () {})
export default class {}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function myFunction() {}
class A {
constructor(xs) {
this.a = xs;
}
}
class A {
constructor(xs) {
this.a = xs;
}
}
class A extends B {
constructor(xs) {
this.a = xs;
}
}
export class A extends B {
constructor(xs) {
this.a = xs;
}
}
export default class A extends B {
constructor(xs) {
this.a = xs;
}
}
var myFunction = () => {}
var myFunction = () => () => {}
var foo = function() {}
const foo = {bar() {}}
var foo = {bar: function() {}}
function foo (abc) {}
function foo () {
return true;
}
module.exports = function quux () {
}
module.exports = function quux () {
}
module.exports = {
method: function() {
}
}
module.exports = {
test: {
test2: function() {
}
}
}
module.exports = {
test: {
test2: function() {
}
}
}
const test = module.exports = function () {
}
const test = module.exports = function () {
}
test.prototype.method = function() {}
const test = function () {
}
module.exports = {
test: test
}
const test = () => {
}
module.exports = {
test: test
}
class Test {
method() {
}
}
module.exports = Test;
export default function quux () {
}
export default function quux () {
}
function quux () {
}
export default quux;
export function test() {
}
export function test() {
}
var test = function () {
}
var test2 = 2;
export { test, test2 }
var test = function () {
}
export { test as test2 }
export default class A {
}
export default class A {
}
var test = function () {
}
window.test = function () {
}
function test () {
}
module.exports = function() {
}
export function someMethod() {
}
export function someMethod() {
}
const myObject = {
myProp: true
};
export interface Foo extends Bar {
baz(): void;
meow(): void;
}
The following patterns are not considered problems:
var array = [1,2,3];
array.forEach(function() {});
function MyClass() {}
function myFunction() {}
var myFunction = function() {};
Object.myFunction = function () {};
var obj = {
myFunction: function () {} };
function myFunction() {}
function myFunction() {}
function myFunction() {}
var myFunction = function () {}
var myFunction = function () {}
var myFunction = function () {}
Object.myFunction = function() {}
Object.myFunction = function() {}
Object.myFunction = function() {}
(function(){})();
var object = {
myFunction: function() {} }
var object = {
myFunction: function() {} }
var object = {
myFunction: function() {} }
var array = [1,2,3];
array.filter(function() {});
Object.keys(this.options.rules || {}).forEach(function(name) {}.bind(this));
var object = { name: 'key'};
Object.keys(object).forEach(function() {})
function myFunction() {
}
function myFunction() {
}
function myFunction() {
}
function myFunction() {
}
function myFunction() {}
var myFunction = function() {}
class A {
constructor(xs) {
this.a = xs;
}
}
class App extends Component {
constructor(xs) {
this.a = xs;
}
}
export default class App extends Component {
constructor(xs) {
this.a = xs;
}
}
export class App extends Component {
constructor(xs) {
this.a = xs;
}
}
class A {
constructor(xs) {
this.a = xs;
}
}
var myFunction = () => {}
var myFunction = function () {}
var myFunction = () => {}
var myFunction = () => () => {}
setTimeout(() => {}, 10);
var foo = function() {}
const foo = {
bar() {}}
var foo = {
bar: function() {}}
var foo = { [function() {}]: 1 };
function foo () {}
function foo () {
return;
}
const test = {};
test.method = function () {
}
module.exports = {
prop: { prop2: test.method }
}
function test() {
}
module.exports = {
prop: { prop2: test }
}
test = function() {
}
module.exports = {
prop: { prop2: test }
}
test = function() {
}
exports.someMethod = {
prop: { prop2: test }
}
const test = () => {
}
module.exports = {
prop: { prop2: test }
}
const test = () => {
}
module.exports = {
prop: { prop2: test }
}
window.test = function() {
}
module.exports = {
prop: window
}
test = function() {
}
test = function() {
}
module.exports = {
prop: { prop2: test }
}
test = function() {
}
test = 2;
module.exports = {
prop: { prop2: test }
}
function test() {
}
test.prototype.method = function() {
}
module.exports = {
prop: { prop2: test }
}
class Test {
method() {
}
}
module.exports = Test;
export default function quux () {
}
export default function quux () {
}
function quux () {
}
export default quux;
function quux () {
}
export default quux;
export function test() {
}
export function test() {
}
var test = function () {
}
var test2 = 2;
export { test, test2 }
var test = function () {
}
export { test as test2 }
export default class A {
}
var test = function () {
}
let test = function () {
}
let test = class {
}
let test = class {
}
export function someMethod() {
}
export function someMethod() {
}
exports.someMethod = function() {
}
const myObject = {
myProp: true
};
function bear() {}
function quux () {
}
export default quux;
export interface Example {
test: string
}
interface Example {
test: string
}
export type Example = {
test: string
};
type Example = {
test: string
};
export enum Example {
test = 123
}
enum Example {
test = 123
}
const foo = {...{}};
function bar() {}
@logged
export default class Foo {
}
const a = {};
const b = {
...a
};
export default b;
export interface Foo extends Bar {
baz(): void;
meow(): void;
}
require-param-description
Requires that each @param
tag has a description
value.
Options
contexts
Set this to an array of strings representing the AST context
where you wish the rule to be applied.
Overrides the default contexts (see below). Set to "any"
if you want
the rule to apply to any jsdoc block throughout your files (as is necessary
for finding function blocks not attached to a function declaration or
expression, i.e., @callback
or @function
(or its aliases @func
or
@method
) (including those associated with an @interface
).
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression ; others when contexts option enabled |
Tags | param |
Aliases | arg , argument |
Options | contexts |
The following patterns are considered problems:
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
The following patterns are not considered problems:
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
require-param-name
Requires that all function parameters have names.
The @param
tag requires you to specify the name of the parameter you are documenting. You can also include the parameter's type, enclosed in curly brackets, and a description of the parameter.
JSDoc
Options
contexts
Set this to an array of strings representing the AST context
where you wish the rule to be applied.
Overrides the default contexts (see below). Set to "any"
if you want
the rule to apply to any jsdoc block throughout your files (as is necessary
for finding function blocks not attached to a function declaration or
expression, i.e., @callback
or @function
(or its aliases @func
or
@method
) (including those associated with an @interface
).
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression ; others when contexts option enabled |
Tags | param |
Aliases | arg , argument |
Options | contexts |
The following patterns are considered problems:
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
The following patterns are not considered problems:
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
require-param-type
Requires that each @param
tag has a type
value.
Options
contexts
Set this to an array of strings representing the AST context
where you wish the rule to be applied.
Overrides the default contexts (see below). Set to "any"
if you want
the rule to apply to any jsdoc block throughout your files (as is necessary
for finding function blocks not attached to a function declaration or
expression, i.e., @callback
or @function
(or its aliases @func
or
@method
) (including those associated with an @interface
).
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression ; others when contexts option enabled |
Tags | param |
Aliases | arg , argument |
Options | contexts |
The following patterns are considered problems:
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
The following patterns are not considered problems:
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
require-param
Requires that all function parameters are documented.
Options
An options object accepts one optional property:
exemptedBy
- Array of tags (e.g., ['type']
) whose presence on the document
block avoids the need for a @param
. Defaults to an empty array.
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression |
Tags | param |
Aliases | arg , argument |
Options | exemptedBy |
Settings | overrideReplacesDocs , augmentsExtendsReplacesDocs , implementsReplacesDocs |
The following patterns are considered problems:
function quux (foo) {
}
function quux (foo, bar) {
}
function quux (foo, bar) {
}
function quux (foo, bar, baz) {
}
function quux (foo, bar, baz) {
}
function quux (foo, bar, baz) {
}
function quux (foo) {
}
function quux (foo, bar) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
export class SomeClass {
constructor(private property: string, private foo: number) {}
}
function quux (foo) {
}
function quux ({bar, baz}, foo) {
}
function quux (foo, {bar, baz}) {
}
function quux ([bar, baz], foo) {
}
function quux (foo) {
}
function assign (employees, name) {
};
The following patterns are not considered problems:
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
class A {
quux (foo) {
}
}
function quux (foo) {
}
class A {
quux (foo) {
}
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
class A {
quux (foo) {
}
}
function quux (foo) {
}
function quux (foo) {
}
const test = something?.find(_ => _)
function foo(req, res, next) {}
function quux () {
}
var A = class {
quux (foo) {
}
}
export class SomeClass {
constructor(private property: string) {}
}
function assign({name, department}) {
}
export abstract class StephanPlugin<O, D> {
public constructor({options, client}: {
options: O;
client: unknown;
}, defaultOptions: D) {
}
}
require-property
Requires that all @typedef
and @namespace
tags have @property
when their type is a plain object
, Object
, or PlainObject
.
Note that if any other type, including a subtype of object such as
object<string, string>
, will not be reported.
Fixer
The fixer for require-example
will add an empty @property
.
| |
---|
Context | Everywhere |
Tags | typedef , namespace |
The following patterns are considered problems:
The following patterns are not considered problems:
function quux () {
}
require-property-description
Requires that each @property
tag has a description
value.
The following patterns are considered problems:
The following patterns are not considered problems:
require-property-name
Requires that all function @property
tags have names.
The following patterns are considered problems:
The following patterns are not considered problems:
require-property-type
Requires that each @property
tag has a type
value.
The following patterns are considered problems:
The following patterns are not considered problems:
require-returns-check
Requires a return statement in function body if a @returns
tag is specified in jsdoc comment.
Will also report if multiple @returns
tags are present.
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression |
Tags | returns |
Aliases | return |
The following patterns are considered problems:
function quux (foo) {
}
function quux (foo) {
}
const quux = () => {}
function quux () {
return foo;
}
const language = {
get name() {
this._name = name;
}
}
class Foo {
bar () {
}
}
function quux () {
}
function f () {
function g() {
return 'foo'
}
() => {
return 5
}
}
The following patterns are not considered problems:
function quux () {
return foo;
}
function quux () {
return foo;
}
function quux () {
return foo;
}
function quux () {
}
const quux = () => foo;
function quux () {}
function quux () {}
async function quux() {}
const quux = async function () {}
const quux = async () => {}
function quux () {
throw new Error('must be implemented by subclass!');
}
function quux () {
throw new Error('must be implemented by subclass!');
}
function quux () {
}
class Foo {
bar () {
}
}
class Foo {
bar () {
}
}
function quux () {
}
function quux () {
}
function quux () {
return undefined;
}
function quux () {
return;
}
function quux () {
return undefined;
}
function quux () {
return;
}
function quux () {
try {
return true;
} catch (err) {
}
return;
}
function quux () {
try {
} finally {
return true;
}
return;
}
function quux () {
try {
return;
} catch (err) {
}
return true;
}
function quux () {
try {
something();
} catch (err) {
return true;
}
return;
}
function quux () {
switch (true) {
case 'abc':
return true;
}
return;
}
function quux () {
switch (true) {
case 'abc':
return;
}
return true;
}
function quux () {
for (const i of abc) {
return true;
}
return;
}
function quux () {
for (const a in b) {
return true;
}
}
function quux () {
for (let i=0; i<n; i+=1) {
return true;
}
}
function quux () {
while(true) {
return true
}
}
function quux () {
do {
return true
}
while(true)
}
function quux () {
if (true) {
return;
}
return true;
}
function quux () {
if (true) {
return true;
}
}
function quux () {
var a = {};
with (a) {
return true;
}
}
function quux () {
if (true) {
return;
} else {
return true;
}
return;
}
require-returns-description
Requires that the @returns
tag has a description
value. The error
will not be reported if the return value is void
or undefined
.
Options
contexts
Set this to an array of strings representing the AST context
where you wish the rule to be applied.
Overrides the default contexts (see below). Set to "any"
if you want
the rule to apply to any jsdoc block throughout your files (as is necessary
for finding function blocks not attached to a function declaration or
expression, i.e., @callback
or @function
(or its aliases @func
or
@method
) (including those associated with an @interface
).
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression ; others when contexts option enabled |
Tags | returns |
Aliases | return |
Options | contexts |
The following patterns are considered problems:
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux () {
}
The following patterns are not considered problems:
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
require-returns-type
Requires that @returns
tag has type
value.
Options
contexts
Set this to an array of strings representing the AST context
where you wish the rule to be applied.
Overrides the default contexts (see below). Set to "any"
if you want
the rule to apply to any jsdoc block throughout your files (as is necessary
for finding function blocks not attached to a function declaration or
expression, i.e., @callback
or @function
(or its aliases @func
or
@method
) (including those associated with an @interface
).
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression ; others when contexts option enabled |
Tags | returns |
Aliases | return |
Options | contexts |
The following patterns are considered problems:
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
function quux () {
}
The following patterns are not considered problems:
function quux () {
}
function quux () {
}
require-returns
Requires returns are documented.
Will also report if multiple @returns
tags are present.
Options
exemptedBy
- Array of tags (e.g., ['type']
) whose presence on the document
block avoids the need for a @returns
. Defaults to an empty array.forceRequireReturn
- Set to true
to always insist on
@returns
documentation regardless of implicit or explicit return
's
in the function. May be desired to flag that a project is aware of an
undefined
/void
return. Defaults to false
.forceReturnsWithAsync
- By default async
functions that do not explicitly
return a value pass this rule as an async
function will always return a
Promise
, even if the Promise
resolves to void. You can force all async
functions to require return statements by setting forceReturnsWithAsync
to true
on the options object. This may be useful for flagging that there
has been consideration of return type. Defaults to false
.contexts
- Set this to an array of strings representing the AST context
where you wish the rule to be applied.
Overrides the default contexts (see below). Set to "any"
if you want
the rule to apply to any jsdoc block throughout your files (as is necessary
for finding function blocks not attached to a function declaration or
expression, i.e., @callback
or @function
(or its aliases @func
or
@method
) (including those associated with an @interface
). This
rule will only apply on non-default contexts when there is such a tag
present and the forceRequireReturn
option is set or if the
forceReturnsWithAsync
option is set with a present @async
tag
(since we are not checking against the actual return
values in these
cases).
'jsdoc/require-returns': ['error', {forceReturnsWithAsync: true}]
| |
---|
Context | ArrowFunctionExpression , FunctionDeclaration , FunctionExpression ; others when contexts option enabled |
Tags | returns |
Aliases | return |
Options | contexts , exemptedBy , forceRequireReturn , forceReturnsWithAsync |
Settings | overrideReplacesDocs , augmentsExtendsReplacesDocs , implementsReplacesDocs |
The following patterns are considered problems:
function quux (foo) {
return foo;
}
const foo = () => ({
bar: 'baz'
})
const foo = bar=>({ bar })
const foo = bar => bar.baz()
function quux (foo) {
return foo;
}
function foo() {}
function bar() {}
async function quux() {
}
const quux = async function () {}
const quux = async () => {}
async function quux () {}
function quux () {
}
function quux () {
}
const language = {
get name() {
return this._name;
}
}
async function quux () {
}
function quux (foo) {
return foo;
}
function quux () {
}
function quux (foo) {
return 'bar';
}
async function foo(a) {
return;
}
async function foo(a) {
return Promise.all(a);
}
The following patterns are not considered problems:
function quux () {
return foo;
}
function quux () {
return foo;
}
function quux () {
}
function quux (bar) {
bar.filter(baz => {
return baz.corge();
})
}
function quux (bar) {
return bar.filter(baz => {
return baz.corge();
})
}
const quux = (bar) => bar.filter(({ corge }) => corge())
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
}
function quux (foo) {
return foo;
}
function quux (foo) {
}
function quux (foo) {
}
function quux () {
return {a: foo};
}
const quux = () => ({a: foo});
const quux = () => {
return {a: foo}
};
function quux () {
}
const quux = () => {
}
function quux () {
}
const quux = () => {
}
function quux () {
}
const quux = () => {
}
class Foo {
constructor () {
}
}
const language = {
set name(name) {
this._name = name;
}
}
function quux () {
}
function quux () {
return undefined;
}
function quux () {
return undefined;
}
function quux () {
return;
}
function quux () {
}
function quux () {
return;
}
function quux (req, res , next) {
return;
}
async function quux () {
}
async function quux () {
}
async function quux () {}
const quux = async function () {}
const quux = async () => {}
class foo {
constructor () {
this.bar = true;
}
}
export default foo;
function quux () {
}
function quux () {
}
async function foo(a) {
return Promise.all(a);
}
async function foo(a) {
return;
}
valid-types
Requires all types to be valid JSDoc or Closure compiler types without syntax errors.
Also impacts behaviors on namepath (or event)-defining and pointing tags:
- Name(path)-defining tags requiring namepath:
@external
, @host
, @name
, @typedef
- Name(path)-defining tags (which may have value without namepath or their
namepath can be expressed elsewhere on the block):
@event
, @callback
,
@class
, @constructor
, @constant
, @const
,
@function
, @func
, @method
, @interface
, @member
, @var
,
@mixin
, @namespace
- Name(path)-pointing tags requiring namepath:
@alias
, @augments
, @extends
, @lends
, @memberof
, @memberof!
, @mixes
, @this
- Name(path)-pointing tags (which may have value without namepath or their
namepath can be expressed elsewhere on the block):
@listens
, @fires
,
@emits
, and @modifies
- Name(path)-pointing tags (multiple names in one):
@borrows
...with the following applying to the above sets:
- Expect tags in set 1-4 to have a valid namepath if present
- Prevent sets 2 and 4 from being empty by setting
allowEmptyNamepaths
to
false
as these tags might have some indicative value without a path
or may allow a name expressed elsewhere on the block (but sets 1 and 3 will
always fail if empty) - For the special case of set 5, i.e.,
@borrows <that namepath> as <this namepath>
,
check that both namepaths are present and valid and ensure there is an as
between them. In the case of <this namepath>
, it can be preceded by
one of the name path operators, #
, .
, or ~
. - For the special case of
@memberof
and @memberof!
(part of set 3), as
per the specification, they also
allow #
, .
, or ~
at the end (which is not allowed at the end of
normal paths).
Options
allowEmptyNamepaths
(default: true) - Set to false
to disallow
empty name paths with @callback
, @event
, @class
, @constructor
,
@constant
, @const
, @function
, @func
, @method
, @interface
,
@member
, @var
, @mixin
, @namespace
, @listens
, @fires
,
@modifies
, or @emits
(these might often be expected to have an
accompanying name path, though they have some indicative value without
one; these may also allow names to be defined in another manner elsewhere
in the block)checkSeesForNamepaths
(default: false) - Set this to true
to insist
that @see
only use name paths (the tag is normally permitted to
allow other text)
| |
---|
Context | everywhere |
Tags | For name only unless otherwise stated: alias , augments , borrows , callback , class (for name and type), constant (for name and type), enum (for type), event , external , fires , function , implements (for type), interface , lends , listens , member (for name and type), memberof , memberof! , mixes , mixin , modifies , module (for name and type), name , namespace (for name and type), param (for name and type), property (for name and type), returns (for type), this , throws (for type), type (for type), typedef (for name and type), yields (for type) |
Aliases | extends , constructor , const , host , emits , func , method , var , arg , argument , prop , return , exception , yield |
Closure-only | For type only: package , private , protected , public , static |
Options | allowEmptyNamepaths , checkSeesForNamepaths |
Settings | mode |
The following patterns are considered problems:
function quux() {
}
function quux() {
}
function quux() {
}
function quux() {
}
function quux() {
}
function quux() {
}
function quux() {
}
function quux() {
}
function foo() {}
function quux() {
}
function quux() {
}
function quux() {
}
const FOO = 'foo';
class Bar {};
let foo;
function quux (foo, bar, baz) {}
function quux () {}
function quux () {}
function quux () {}
let foo;
The following patterns are not considered problems:
function quux() {
}
function quux() {
}
function quux() {
}
function quux() {
}
function quux() {
}
function quux() {
}
function quux() {
}
function quux() {
}
function quux() {
}
function quux() {
}
function quux() {
}
function quux() {
}
function quux() {
}
function quux() {
}
function quux() {
}
const FOO = 'foo';
const FOO = 'foo';
class Bar {};
class Bar {};
let UserDefinedGCCType;
function quux (foo, bar, baz) {}
function quux () {}
function quux () {}
function quux () {}
function quux () {}
function quux () {}